Skip to content

Conversation

@technophile-04
Copy link
Collaborator

Description

Noticed this while testing #756, it was caused in #758 :

Screen.Recording.2024-03-10.at.10.03.32.AM.mov

When you get an error while sending transaction, it shows notification two times, this is due to since in #758, we are not eating up error in useTransactor instead showing notification + throwing it forward.

In 2746877 removed our own showing of notification or error again since its same already shown in useTransactor

For more details checkout : #758 (review)

Copy link
Member

@rin-st rin-st left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

Copy link
Collaborator

@Pabl0cks Pabl0cks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch, gj Shiv! Looks good to me 🙌

@technophile-04
Copy link
Collaborator Author

Tysm guys ! Merging this 🙌

@technophile-04 technophile-04 merged commit 6d0ac6c into main Mar 11, 2024
@technophile-04 technophile-04 deleted the bug/WriteOnlyFunction-two-errors branch March 11, 2024 09:44
@github-actions github-actions bot mentioned this pull request Mar 11, 2024
technophile-04 added a commit to BuidlGuidl/abi.ninja that referenced this pull request Jun 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants